Wireless communication enabled meter and network

ABSTRACT

A meter enabled for wireless communication and a wireless communication network are disclosed. A meter enabled for wireless communication comprises a metering device, a wireless communication system and an interface between the two. Meter data can be read, and the meter can be controlled via communication with a wireless network using, e.g., the Bluetooth™ protocol. A self-configuring wireless network is also disclosed. The wireless network includes a number of vnodes, and one or more VGATES. The vnodes are devices that are enabled for wireless communication using, e.g., the Bluetooth™ protocol. Vnodes are operative to form ad hoc piconet connections. The one or more VGATES comprise computer network gateways that are enabled for wireless communication using, e.g., the Bluetooth™ protocol. Thus, the VGATES enable the wireless array of vnodes to communicate with a private or public computer network to transmit data or receive commands. The network may also communicate with a VNOC system. VNOC is a universal communications adapter that enables the wireless array of vnodes to communicate (either directly or through a VGATE) with a central control facility via various wireless or wired communication media.

This application is a continuation of non-provisional application Ser.No. 13/227,590, filed Sep. 8, 2011, which is a continuation ofnon-provisional application Ser. No. 12/030,527, filed Feb. 13, 2008,which is a continuation of non-provisional application Ser. No.10/040,150, filed Jan. 2, 2002, which is a continuation ofnon-provisional application Ser. No. 09/774,121, filed Jan. 31, 2001 anda continuation in part of non-provisional application Ser. No.09/621,965, filed Jul. 21, 2000. Non-provisional application Ser. No.09/774,121 claims priority to provisional application No. 60/179,046,filed Jan. 31, 2000, and provisional application No. 60/179,041, filedJan. 31, 2000. Each of the above-identified patent applications isincorporated herein by reference, in its entirety, for all purposes.

FIELD OF THE INVENTION

This invention relates to a meter that is enabled for wirelesscommunication. More specifically, this invention relates to a meter,such as a utility meter, that is enabled for wireless communication. Theinvention also relates to a self-configuring, wireless network thatenables data capture at a plurality of metering sites and wirelesstransmission of the captured data from the plurality of metering sitesto one or more collection points.

BACKGROUND OF THE INVENTION

Remote communication with meters is known, for example, for home loadcontrol and for usage monitoring. Commands for home load control aretypically transmitted over telephone lines or power lines.Communicating, via power lines or telephone lines is slow and subject tophysical disruption. Moreover, communicating via power lines ortelephone lines presents the possibility of spurious signals,cross-talk, and other interference. One-way or two-way radios are alsosometimes used. Both are expensive and two-way radios also require alicense.

With regard to usage monitoring, on the other hand, utility meters arenormally read by a person visiting the meter. In recent years, a numberof schemes have been contemplated to accumulate usage data, as bycounting wheel revolutions per unit time and storing such information asa preliminary necessity for actually automatically transmitting suchinformation upon command of a remote central station.

Local area networks that interconnect via cables are also known. Thesenetworks are expensive to install and somewhat intrusive in that cablesmust be run to physically interconnect the various nodes in the network.Moreover, networks that are interconnected with cables are subject tophysical disruption of the cables.

Recently, wireless networks have been developed. These networks can beused to collect information from, and to disseminate information toindividual nodes of the network. For example, conventional wirelessnetworks generally operate using a loop configuration in which each nodein the network is interconnected and communicates only with twoneighboring nodes. Information and/or commands are passed from node tonode around the loop until they arrive at a master node. The master nodeis used to communicate information that is gathered to a centralstation, or to accept and distribute information received from a centralstation throughout the network.

Conventional wireless networks, however, have limitations as well. Forexample, because conventional wireless networks generally have a loopconfiguration, when one node is disabled, the integrity of the entirenetwork is affected. Moreover, if the master node of such a conventionalnetwork is disabled, the network becomes isolated.

These and other drawbacks exist with current systems.

SUMMARY

An object of the invention is to overcome these and other drawbacks inexisting systems.

Another object of the invention is to provide a meter that is enabledfor wireless communication.

Another object of the invention is to provide a self-configuringwireless network.

According to one embodiment, a wireless communication enabled meter isdisclosed. A meter enabled for wireless communication comprises ametering device, a wireless communication system and an interfacebetween the two. The metering device is a standard programmable meteringdevice that can measure usage data and control usage. The wirelesscommunication system is enabled for wireless communication using, e.g.,the Bluetooth™ protocol. The interface facilitates communication betweenthe metering device and the communication system so that meter data canbe read with a wireless network using, e.g., the Bluetooth™ protocol.

According to another embodiment, a self-configuring wireless network isdisclosed. The wireless network comprises a number of virtual nodes(“vnodes”), and one or more virtual gates (“VGATES”). Vnodes areoperative to form ad hoc piconet connections. Vnodes can comprise avariety of devices. Data traveling through the network is passed fromone or more ad hoc piconets to one or more of the anodes or an uploadingpoint, e.g., a VGATE. If a node is not connected to a piconet, or if itsconnection to a piconet has been disturbed, the vnode executes aself-configuration routine to connect itself with another piconet. Thisself configuration process is based on a set of rules. The one or moreVGATES comprise computer network gateways enabled for communication.

Other features and advantages of the present invention will be apparentto one of ordinary skill in the art upon reviewing the detaileddescription of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a wireless communication enabled meter.

FIG. 2 is a schematic depiction of a self-configuring, wireless networkaccording to another embodiment of the present invention.

FIG. 3 is a schematic depiction of a self-configuring, wireless networkaccording to another embodiment of the present invention.

FIG. 4 is a schematic depiction of a self-configuring, wireless networkaccording to another embodiment of the present invention.

FIG. 5 is a schematic diagram showing, a self-configuration processaccording to one embodiment of the present invention.

FIG. 6 is a schematic diagram showing a self-configuration processaccording to one embodiment of the present invention.

FIG. 7 is a schematic diagram showing a self-configuration processaccording to one embodiment of the present invention.

FIG. 8 is a schematic diagram showing a self-configuration processaccording to one embodiment of the present invention.

FIG. 9 is a schematic representation of the system for an embodiment ofthe invention.

FIG. 10 is a black box representation of an embodiment of the invention.

FIG. 11 is a black box representation of another embodiment of theinvention.

FIG. 12 is a schematic representation of components of the system for anembodiment of the invention.

FIG. 13A is a schematic of an embodiment of the VNOC architecture for anembodiment of the invention.

FIG. 13B is a schematic of an embodiment of network architecture.

FIG. 14 is a black box representation of an embodiment of the inventionemploying redundant architecture.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 schematically depicts a meter 1 that is enabled for wirelesscommunication. Meter 1 may comprise metering device 2, interface 3 andwireless communication transceiver 4. In operation, metering device 2may communicate with wireless communication transceiver 4 via interface3. Wireless communication transceiver 4, in turn, may communicate withother wireless communication enabled devices, for example, other meters1 or a central station. Wireless communication transceiver 4 may beoperative to transmit data to and receive data from other meters 1equipped with transceivers 4.

Metering device 2 operates to measure and regulate the usage of someutility, e.g., natural gas, electricity, or water. According to oneembodiment, metering device 2 comprises any known metering devicecapable of producing an analog or digital output signal indicative ofutility usage. In another embodiment, metering device 2 comprises ametering device capable of accepting an analog or digital input signaland for monitoring and controlling utility usage. For example, meteringdevice 2 is operative to monitor utility usage. Utility usage data isuseful in the electrical industry, for example, to control futuregeneration in order to avoid over generation or under generation ofelectricity. According to another example, metering device 2 isoperative to monitor power quality. The power factor of electricalpower, for example, may vary with usage. Metering device 2 can monitorthis variance. In turn, household devices that are also enabled forwireless communication can be controlled to change the load and correctthe power factor. According to one particular embodiment, meteringdevice 2 comprises the Altimus™ produced and sold by Landis & GyrUtilities Services, Inc.

Interface 3 facilitates communication between meter 1 and wirelesscommunication transceiver 4. According to one embodiment, interface 3receives digital signals from wireless communication transceiver 4 andin response produces digital control signals for meter 1 and/or meteringdevice 2. Interface 3 also receives digital signals from metering device2 and outputs digital signals suitably formatted for transmissionthrough wireless communication transceiver 4. According to oneembodiment, interface 3 comprises a software module. According toanother embodiment, interface 3 is implemented in firmware or hardware.Conventional interfaces may be employed as interface 3 in someembodiments of the invention.

Wireless communication transceiver 4 operates to wirelessly transmit andreceive data and other information. According to one embodiment,wireless communication transceiver 4 is operative to receive controlinformation and to transmit usage data accumulated by metering device 2.According to one particular embodiment, wireless communicationtransceiver 4 comprises a Bluetooth™ communication chip. Bluetooth™ isexplained in detail in Bluetooth [sic] Document Page (visited Nov. 15,1999), <http://www.bluetooth.com/document/default.asp?page=overview>(Bluetooth™ Specification), herein incorporated by reference. Accordingto another embodiment, wireless communication transceiver 4 comprises atransceiver operative to communicate using another suitable wirelesstransmission protocol, such as an ultrawide band protocol.

Briefly, Bluetooth™ is a wireless communication protocol operating inthe unlicensed ISM band at 2.4 GHz that enables wireless communicationof data and voice. The Bluetooth™ system operates through a collectionof short-range radio links, built into 9.times.9 mm microchips, i.e.,Bluetooth™ chips. The short-range radio links enable ad hoc groupings ofconnected devices away from fixed network infrastructures.

Bluetooth™ uses an acknowledgment and frequency hopping scheme to makenetwork links robust. Specifically, Bluetooth™ radio modules avoidinterference from other signals by hopping to a new frequency aftertransmitting or receiving a packet of data. The Bluetooth™ radio usesfaster hopping and shorter packets than other systems operating in thesame frequency band. Short packages and fast hopping make the Bluetooth™system robust, e.g., by limiting the impact of domestic and professionalmicrowave ovens and other potential sources of interference.

Bluetooth™ uses Forward Error Correction (FEC) to limit the impact ofrandom noise on long-distance links. The encoding is optimized for anuncoordinated environment. A frequency hop transceiver is applied tocombat interference and fading. A shaped, binary FM modulation isapplied to minimize transceiver complexity. The gross data rate is 1Mb/s. A Time-Division Duplex scheme is used for full-duplextransmission.

The Bluetooth™ baseband protocol is a combination of circuit and packetswitching. Slots can be reserved for synchronous data packets. Each datapacket is transmitted in a different hop frequency. A packet nominallycovers a single slot, but can be extended to cover up to five slotsBluetooth™ supports an asynchronous data channel, up to threesimultaneous synchronous voice channels, or a channel whichsimultaneously supports asynchronous data and synchronous voice. Eachvoice channel supports 64 kb/s synchronous (voice) link. Theasynchronous channel can support an asymmetric link of maximally 721kb/s in either direction while permitting 57.6 kb/s in the returndirection, or a 432.6 kb/s symmetric link.

Using Bluetooth™, meter 1 transmits data to, for example, a centralcollection point via other Bluetooth™ enabled devices (e.g., otherBluetooth™ enabled meters) forming an ad hoc network Moreover, meter 1receives data from a central controller via other Bluetooth™ enableddevices through a similar type of ad hoc network.

According to another embodiment of the present invention, aself-configuring (i.e., ad hoc) wireless network is disclosed. Aself-configuring wireless network may be advantageously formed using thewireless communication enabled meters disclosed in conjunction withFIG. 1. A self-configuring wireless network will be explained in moredetail in connection with FIG. 2.

FIG. 2 schematically depicts an embodiment of a self-configuringwireless network 20 according to the present invention. Network 20 maycomprise a number of piconets 21 and a VGATE 22. Each piconet 21 maycomprise a plurality of individually addressable vnodes 23 that arewirelessly linked together. For example, in a Bluetooth™ system, apiconet may comprise a plurality of Bluetooth™ units sharing a commonchannel.

According to one embodiment, network 20 comprises a number of layers.The layers may include (1) A layer for configuring the network. Thislayer is used to establish and support connections between the variousvnodes 23 to VGATE 22. (2) A layer for upstream communications, i.e.,communications from vnodes 23 to VGATE 22. And, (3) A layer fordownstream communications, i.e., communications from a central computernetwork to vnodes 23 through VGATE 22.

These layers may be in addition to the layers that may be present in aparticular wireless communication transport agent that may be used.According to one particular embodiment, these three layers areestablished using the proprietary Telemetry Technologies CommunicationsProtocol™ (“TTCOM™”) established by Telemetry Technologies.

TTCOM™ is a communications protocol used for inter-device communicationsfor Telemetry Technologies™ products. TTCOM™ does not explicitly specifythe transport media of communication between devices. The physical anddata layer capabilities may be device specific and may be modified tosuit different hardware needs. For example, TTCOM™ may be implemented ona Serial RS232 link, a SPI bus connection, a parallel interface, a radionetwork, a network connection (TCP/IP), the Internet or any other meansused to exchange octets reliably between two devices.

The TTCOM™ may be peer-to-peer, i.e. all devices are equal and can queryeach other. All communications may be in a half-duplex Poll Response(client/server) format, i.e. each query from a client device maygenerate a response from the server device. Only one request from anyclient to any server may be outstanding at anytime. TTCOM™ may beimplemented as a hierarchical master/slave protocol at the applicationlevel, if desired.

According to another embodiment, Bluetooth™ is used as the wirelesscommunication transport agent.

In operation, each vnode 23 receives command or other data through adhoc network 20, one instance of which is shown in FIG. 2. For example,command data may be transmitted through VGATE 22 to piconets 21. Thedata is passed through the various piconets 21 until it arrives at thepiconet 21 which contains the destination vnode 23. Network 20 can alsobe used to collect information from vnodes 23. For example, as will beexplained in more detail below, vnodes 23 may comprise devices that aredesigned to collect data. Collected data may be passed through thevarious piconets 21 until arriving at VGATE 22. From VGATE 22, collecteddata may be passed to a private or public computer network, such assystem 26. Alternatively, data arriving at VGATE 22 may be passed toVNOC 25 where it can be uploaded to, for example, system 26, via avariety of wireless communication methods as will be explained in moredetail below.

Vnodes 23 comprise individually addressable entities enabled forwireless communication. Vnodes 23 can be originators, recipients orrouters of data. According to one embodiment, each vnode 23 has its ownIP address so that commands can be sent to and data can be collectedfrom individual vnodes through VGATE 22. As will be explained in moredetail below, VGATE 22 may be a computer gateway that enablescommunications between public or private computer networks 26 andnetwork 20. According to one embodiment, vnodes 23 maintain a routingtable with information about two separate groups of entities. The firstgroup comprises vnodes 23 that are potential gateways for this vnode.Typically, one of the vnodes in this list has an acknowledged activeroute to a gateway such as VGATE 22. According to one embodiment, thisroute is stored in non-volatile memory so that a vnode may attempt toestablish a connection so with VGATE 22 without going through theself-configuration process described below. The second group comprisesvnodes 23 that have a confirmed route to a gateway using this vnode asan intermediate hop. The concept of hops to a gateway is explained inmore detail below in conjunction with the self-configuring process.

According to one embodiment, a vnode 23 comprises a device enabled forwireless communication using the Bluetooth™ protocol. According to thisembodiment, vnode 23 may communicate with any other Bluetooth™ enableddevice. For example, in one particular embodiment, a vnode 24 comprisesa meter enabled for wireless communication using the Bluetooth™ protocolas explained in conjunction with FIG. 1. According to other embodiments,a vnode 23 may comprise a vending machine, an alarm system or electricdistribution equipment.

As explained in the Bluetooth™ Specification, Bluetooth™ uses a numberof multiplexed communication channels to communicate between devices.Each channel comprises a slightly different transmission frequency.According to the embodiment of network 20 shown in FIG. 2 in which eachof vnodes 24 comprises a Bluetooth™ enabled device, two of theBluetooth™ communication channels may be reserved for data passingbetween piconets 21. One channel can be used for upstream communicationand the second channel can be used for downstream communication. In thisway, upstream communication and downstream communication may be handledsimultaneously. When data is passed between two piconets 21 in onedirection, the vnode 23 of the piconet 21 that is engaged in thecommunication can determine if there is data to be passed in the otherdirection and may pass any such data off to the vnode 23 from which itreceived data. The use of other wireless communication protocols ispossible.

Piconets 21 are operative to relay data to and from a central collectionpoint through VGATE 22 using the wireless communication capabilities ofvnodes 23 explained above. Piconets 21 may comprise, for example, ad hocwireless networks of up to eight vnodes 23. Each vnode 23 in a piconet21 at any instant of time knows about the existence of the other vnodes23 that are connected to the piconet 21. In particular, each vnode 23may know the identities (e.g., the IP address) of the other vnodes 23and the type of data at the other vnodes 23 that are connected topiconet 21. This facilitates the above-described passing of data to andfrom the individual vnodes 23 and among piconets 21. More specifically,communications between piconets 21 need only take place through one ofthe vnodes 23 in a piconet 21 to one of the vnodes 23 in another piconet21. According to another embodiment, any other suitable number of vnodesmay be used to form piconets 21 given the limits of the communicationprotocol being used and the hardware.

As schematically depicted in FIG. 2, each of the rows of vnodes 23 mayform a 15 piconet 21. Data passing through the network 20 “hops” fromone piconet 21 to another piconet 21 via wireless connections as shownin FIG. 2. These wireless connections are depicted at a particularinstant in time and may change as piconets 21 are reconfigured. Datatravels until it reaches the appropriate destination which may be VGATE22 for data traveling upstream or one or more of vnodes 23 (or anotherBluetooth™ enabled device) for data traveling downstream.

Because data sharing takes place among the various vnodes 23 of apiconet 21, network 20 of the present invention may also includesecurity measures to protect the data of each vnode 23. According to oneembodiment, the IP address of each vnode 23 comprises an encryption keythat is used by each particular vnode to decode incoming data. The sameencryption scheme may be used to encode all outgoing data from any vnode23 as well. In this way, although each vnode 23 of a piconet 21 hasaccess to the data for each of the other vnodes 24 of a piconet 21, thedata is in encrypted form. Thus, the data is unreadable to the othervnodes 23 of the piconet 21.

Returning to FIG. 2, VGATE 22 operates to manage network 20. As managerof network 20, VGATE 22 may comprise both a communication gateway and anadministrator for network 20. As a communication gateway, VGATE 22comprises a gateway that enables wireless network 20 to communicate witha private computer network or a public computer network such as theInternet. According to one embodiment, VGATE 22 comprises a standardcomputer gateway enabled for Bluetooth™ communication. According to thisembodiment, VGATE 22 may communicate with network 20 wirelessly usingthe Bluetooth™ protocol. Further, VGATE 22 may communicate with a publicor private computer network using conventional means (wiredcommunication). In operation, VGATE 22 can receive information, such ascontrol data, from a private computer network and retransmit thatinformation to any of vnodes 23 through network 20 using the Bluetooth™protocol. Further, VGATE 22 can receive data from any of vnodes 23 vianetwork 20 using the Bluetooth™ protocol and then retransmit thatinformation through a private computer network. Other embodiments ofVGATE 22 are possible.

According to another embodiment, VGATE 22 may be enabled to communicateusing a number of separate wireless devices. Thus, the number of vnodes23 that any VGATE 22 may act as a gateway for is increased According toone embodiment, VGATE 22 is equipped with two or more Bluetooth, chipsand its capacity is at least doubled.

VGATE 22 may also act as an administrator for network 22. Specifically,VGATE 22 may comprise intelligence about the configuration of network20. According to one embodiment, VGATE 22 comprises an intelligencemodule that contains the geographic location of all vnodes 23 within acertain distance of VIGATE 22 and a list of all vnodes 23 that arepresently communicating with VGATE 22. This is useful for example forlocating specific vnodes 23, for example, for service purposes. Forexample, assume each vnode 23 represents a utility meter 21 in aresidential neighborhood. If one of the meters 21 is not functioningproperly, a repair person can determine the location of the vnode 23from VGATE 22. Alternatively, if a repair person is driving through theneighborhood, that person can connect to network 20 using theconfiguring process (explained below) as a vnode 23 would. Onceconnected, the repair person can use VGATE 22 to locate thenon-functional vnode 23.

Although only a single VGATE 22 is shown in FIG. 2, network 20 maycomprise a number of VGATES 22. Because VGATE 22 acts as a communicationhub for network 20, the number of VGATES 22 in any network 20 willdepend upon the bandwidth available. As described above, when data ispassed through each piconet 21, it is determined whether additional datais to be passed. Thus, when data is passed through each piconet 21,additional content may be added to the data being passed. Therefore, tohelp ensure that the bandwidth limitations of the communication protocolare not exceeded, a sufficient number of VGATES 22 are deployed througha network 20.

In another embodiment, shown in FIG. 3, at least two networks 31-37 maybe daisy chained together to form a network cluster, such as networkcluster 39. For example, each network 31-38 may represent a separatebuilding. Thus, each building network 31-38 may be connected to anotherbuilding network through individual vnodes 30 a-30 h. In thisembodiment, the network cluster may be connected to one VGATE 22.

Thus, a first network 34 may be connected to a first VGATE 22 and asecond network 33 may be connected to the first network by connecting afirst vnode 30 a in the first network to a second vnode 30 b in thesecond network. Additional networks 31, 32 may be added to the networkcluster where each network 31-34 communicates with the first VGATE 22through the network cluster connections (i.e. network 31 communicates toVGATE 22 through networks 32, 33 and 34 while network 34 communicatesdirectly with VGATE 22).

In another embodiment, networks 31-38 need not create a daisy chain pathto communicate to a VGATE 22 through the geographically nearest network.For example, a network 38 may communicate to a VGATE 22 through anetwork 35 although network 35 is not the geographically nearest networkto network 38.

In a further embodiment, the direct path formed from the VGATE 22 to avnode 30 a-h or network 31-38 need not be from the VGATE 22 to thenearest vnode 30 a-h or network 31-38. For example, network 37 may forma direct path to VGATE 22 through vnode 30 g although network 37 is notthe geographically nearest network to VGATE 22.

Referring to FIG. 2, system 26 may comprise a central controller. VGATE22 may facilitate connection to a central control controller 26.According to one embodiment, where vnodes 23 comprise utility meters 21,a utility company may read the meters 21 remotely and control utilityusage by communicating with network 20 through VGATE 22. The centralcontroller in this embodiment may be the computer network of the utilitycompany. According to another embodiment, vnodes 23 may comprise vendingmachines and a management company can monitor stock in the vendingmachines by communicating with the machines through network 20 usingVGATE 22. In this embodiment, the central controller may be the computersystem for the management company. In another embodiment, VGATE 22 mayfacilitate communication between a monitoring company and a network ofalarm systems when vnodes 23 are residential or commercial alarmsystems. In still another embodiment, VGATE 22 may facilitatecommunication between an electric generation company and itsdistribution equipment that are enabled to communicate using a wirelesscommunication protocol.

Returning to FIG. 2, network 20 may also connect with other devices.FIG. 2 depicts network 20 connecting with VNOC 25 and other devices 24that are enabled for wireless communication. Each is explained in moredetail below.

As discussed above, VGATE 22 facilitates communication between network20 and other public or private computer networks using, e.g.,conventional wired networking. In contrast, VNOC 25 comprises a virtualnetwork operation center. According to one embodiment, VNOC 25 comprisesa universal communication adapter that is enabled to transmit andreceive using a variety of communication protocols and media VNOC 25 iscapable of communicating using RF, cellular, microwave, satellite andother communication protocol. According to one embodiment, VNOC 25communicates with VGATE 22 in order to facilitate communication betweennetwork 20 and other non-wired networks. For example, VNOC 25 canreceive command data for network 20 via satellite communication andretransmit the command data to VGATE 22 for distribution to vnodes 23.According to one particular embodiment, VNOC 25 comprises the VNOCsystem sold by Telemetry Technologies, Inc.

According to another embodiment, VNOC 25 may communicate directly withvnodes 23. In this embodiment, VNOC 25 is enabled for communicationusing the Bluetooth™ communication protocol. For example, VNOC 25 mayreceive command data for any of vnodes 23 via any of its enabledcommunication protocols. VNOC 25 may then retransmit the command data tothe appropriate vnode using the Bluetooth™, protocol. Conversely, VNOC25 may receive collected data from one or more of vnodes 23 via network20 using the Bluetooth™ protocol and then retransmit the collected datato another location using an appropriate one of its enabledcommunication protocols. Accordingly, VNOC 25 enables communication withdevices forming part of network 20 using a number of differentcommunication protocol or media. VNOC 25 is especially useful fornetworks 20 installed in remote or rural areas where hard wireconnections are uneconomical. A detailed description of VNOC 25 isprovided in conjunction with FIGS. 7-12 below.

Network 20 may also connect with other devices 24. These other devices24 are similar to vnodes 23 in that they are enabled for wirelesscommunication. According to one embodiment, these other devices 24 aredissimilar from vnodes 23 in that they do not have the capability toconnect as members of piconets 21. These other devices 24 are able tocommunicate through network 20 by connecting to a vnode 23 as shown inFIG. 2. According to one embodiment, these other devices may comprisedevices that are enabled to communicate using the Bluetooth™ protocol.In a particular embodiment, these other devices may comprisethermostats, pool pumps, and other household devices (refrigerators,washers, dryers, electronics) that are enabled to communicate using theBluetooth™ protocol. According to another embodiment, these otherdevices are enabled to form piconets 21 and act as vnodes 23.

According to one embodiment, network 20 is formed by deploying utilitymeters that are enabled for wireless communication throughout aneighborhood. The utility meters act as vnodes 23 to establish theinfrastructure of network 20. Once network 20 is deployed, it may beused to control other household devices such as pool pumps, thermostatsand appliances (other devices 24) that are also enabled for wirelesscommunication. According to one particular embodiment, Bluetooth™enabled meters are deployed throughout a neighborhood to form theinfrastructure for network 20. Network 20 is then used to communicatewith other Bluetooth™ enabled devices in the neighborhood.

In another embodiment, shown in FIG. 4, the network 20 may be a widearea network to optimize communication in rural areas. Network 20 mayinclude piconets 21 a, 21 z. As shown, piconet 21 z is a distance D fromits geographically nearest piconet 21 a in network 20. High gain,directional antennas 41-42 may be used to provide a line of sight pointto point connection between vnode 23 a of piconet 21 a and vnode 23 z ofpiconet 21 z. Antennas 41-42 form fixed links, and boost decibel gainand power in the network 20. Use of antennas 41-42 to form connectionsbetween Anodes 23 a, 23 z allows the range from the Bluetooth™ equipmentto be increased to at least approximately 17 miles.

As discussed in the background, conventional wired networks suffer fromdrawbacks such as physical disruption. One advantage of the embodimentsof wireless network 20 discussed above is that it does not depend onwired connections. Another advantage of wireless network 20 discussedabove is its self configuring nature. Therefore, if there is aninterruption in the network structure, the network can reconfigureitself. More specifically, each of vnodes 23 is programmed toperiodically poll the other vnodes 23 of its piconet 21 to determinethat piconet 21 is still intact. If a vnode 23 determines through itsregular polling routine that it is no longer connected to a piconet 21,it performs a self-configuring cycle in which it looks for anotherpiconet 21 to join.

The self-configuring cycle of a vnode 23 within network 20 is based on anumber of rules. One example of such a rule is that a vnode 23 in searchof a piconet 21 will only connect with a piconet 21 that is in search ofa vnode 23. As another example, each vnode 23 within network 20 may beprogrammed with a maximum of hops that it can use in order to reach acommunication point (VGATE 22 or VNOC 25). The maximum number of hopsfor any vnode 23 is preferably based on geography. That is, when a vnode23 is deployed, it may be programmed with information concerning thegeographic location of the closest uploading point. Therefore, by rule,when a vnode 23 goes through its polling routine, it can be instructednot to connect to any piconet 21 if the connection would result in amaximum number of hops to a VGATE 22 or VNOC 25 equal to, or greaterthan, its maximum number of hops. Moreover, a vnode 23 may be programmedto connect to a piconet 21 that has the smallest number of hops to anuploading point. As still another example of a self-configuring rule,when a vnode 23 is looking for a piconet 21 to connect with, it may beprogrammed to connect with piconets 21 that have connections to two ormore other piconets 21. In this way, a measure of redundancy can bebuilt into self-configuring network 20. Other rules are possible and arewithin the skill of the ordinary artisan.

According to another embodiment, any particular vnode 23 may connectwith multiple networks 20 at any given instant in time. As explainedabove, according to one embodiment, self-configuring network 20 utilizestwo communication channels available within the Bluetooth™ communicationprotocol for upstream and downstream communication. According to anotherembodiment, however, multiplexing is used in conjunction with those twocommunication channels allowing each vnode 23 to be part of a number ofdifferent networks 20 at the same time.

With reference to FIGS. 3-6, an example of self configuration of network20 will now be given. For the example shown, it will be assumed that allvnodes 23 in network 20 are UNCONFIGURED (represented by white circles).The circles in FIGS. 5-8 represent either individual vnodes 23 orpiconets 21. As shown in FIG. 5, in the first step when vnodes 23bootup, they wait a pseudo-random amount of time (to avoid networkflooding after a global power down) before broadcasting a request for aVGATE. The vnodes then wait for a valid response from other vnodes tosetup their routes. If no valid response is received, the requestmessage is again broadcast after a pseudo-random delay. This process isrepeated till a valid response is received from another vnode 23. Duringthis time if the vnode 23 receives a message from a VGATE it stopsbroadcasting the request message and stores the transport-agentsparameters for access to the VGATE 22 in its routing table. In theexample shown, as vnodes a-m are broadcasting requests for a VGATE,VGATE v may be broadcasting a message identifying itself as a VGATE.

As shown in FIG. 6, in the next step of network configuration, vnodes j,k, l and m successfully receive a message being periodically broadcastedby VGATE 22. These vnodes 23 update their routing tables and stopbroadcasting the request message. These vnodes are now configured with azero metric. The metric indicates that these vnodes 23 have a directlink to VGATE 22.

Vnodes a-i may continue broadcasting request messages afterpseudo-random delays. VGATE v may continue broadcasting a messageidentifying itself as a VGATE.

Now, some of the vnodes 23 that have a route to the VGATE 22 configured,receive a request messages from unconfigured vnodes 23 and choose torespond with a message indicating their availability as a path to aVGATE v. The metric in their response is set to 1. For example, vnodesj-m may respond to vnodes e-i. Vnodes 23 which receive this responsemessage can choose to update their routing table with the new path. Onthe other hand, if the metric, usage or transport-agent providedparameter (e.g. radio signal strength) is unacceptable the vnodes cansimply discard the response and wait for responses from other vnodes.For example, vnode e receives a response from vnode k providing a routeto VGATE v, but the metric is too high. This is illustrated in FIG. 7.In the example shown, vnodes f-i have multiple routes, based on metrics.The dotted lines represent discarded routes. The primary gateways may besent acknowledgements.

This process continues until all vnodes are configured. The completionof the configuration process is shown in FIG. 8. It should be noted thateach of the vnodes shown in FIGS. 5-8 may represent individual vnodes 23or the vnodes pictured may actually represent individual piconets 21. Itshould also be noted that any vnode a-m, not only the geographicallynearest vnodes, may connect directly to VGATE v. For example vnode d maybe directly connected to VGATE v.

When undergoing this self-configuration process, vnodes establishconnections with each other. According to one embodiment, theseconnections are established between two vnodes using a three stephandshake. For example, assume a connection is being established betweenvnode X (desiring a route) and vnode Y (providing a route).

Step 1 vnode X broadcasts request for route to VGATE.

Step 2 vnode X possibly receives multiple replies from various vnodes.It chooses vnode Y to be its Gateway (based on metric andtransport-agent parameters).

Step 3 vnode X acknowledges to vnode Y confirming that Y is now theGateway for X.

Once this route has been established, X and Y are able to exchangemessages and depending on the transport agent periodically check eachother for messages to be exchanged. In case there is an error (a vnodefails, or communications fails) it is then the responsibility of vnode Xto find another route by sending out a request. A vnode can explicitlysend a message to a VGATE requesting a deletion of a route by sending amessage.

Data propagation through network 20 will now be explained in moredetail. Data propagates through network 20 in individual packets.According to one embodiment, packets to be sent to VGATE 22 have adestination of zero. The vnode 23 that originates the packet sends thepacket through its gateway path vnode to vnode until the packet reachesVGATE 22. Each vnode 23 processing the packet decrements the address ofthe packet. If the address reaches zero, the packet is discarded. Thisis a mechanism to avoid looping packets in circular paths. As thepackets pass through each vnode 23, an entry is made in the packet torecord the route of the packet. The route is stored in VGATE 22 andprovides a path for data directed from VGATE 22 to the vnode 23.

A packet exchange between nodes can be done in an acknowledge ornon-acknowledge mode. Sending data in an acknowledge mode helps ensurethat the packet is delivered to its intended recipient. According to oneembodiment, acknowledgements are piggybacked on other data travelingthrough network 20 to reduce network traffic.

If a packet delivery fails, e.g., due to a vnode 23 failure, the vnode23 delivering the packet starts a new search for a path to VGATE 22 bysending out a request, just as if it was a new vnode 23. Additionally,it should be noted that a VGATE 22 can delete a route at any time, e.g.,to preempt excess traffic problems. VGATE 22 typically does notterminate any packet delivery until receiving acknowledgements from allvnodes. A vnode may search for a path to a VGATE 22 at any time, even ifit is configured. This enables a vnode 23 to search for a more efficientpath and thus enables the network to fine tune itself. As stated above,vnodes 23 may store a preferred route in non-volatile storage andattempt to establish this route directly without searching for a link.

As explained above, network 20 comprises a three layer network on top ofan existing transport agent such as Bluetooth™. According to anotherembodiment, one or more additional layers may be added. According to oneparticular embodiment, a layer may be added to form networks betweenvarious VGATES 22. This layer would enable, among other things, thecapacity of network 20 to be increased.

VNOC 25 will now be explained in conjunction with FIGS. 9-14. Typically,the VNOC system is intended to provide seamless service for thecustomer. For example, the is following description of one embodiment ofthe VNOC system is provided with reference to a remote water metercontroller. The water metering customer has a remotely located watersupply implementing a remotely controllable water metering valve. Thecustomer desires to control the metering valve, monitor its status, andcollect other data pertaining to the valve (e.g., daily throughput,average water temperature, or other data). If a particular circumstanceshould occur (e.g., the water flow drops below a predetermined level),the water valve meter sends a signal in whichever format the remotecontroller implements (e.g., cellular, wireline, Internet, or otherformat). The VNOC system provides the interface to receive data from theremote valve in that format and records the occurrence of an incomingevent. The VNOC translates the incoming event into the outgoing eventformat (or formats) pre-selected by the customer. If the incoming eventis one that the customer designated as requiring notification, theselected notification report is sent to the customer over theappropriate customer interface (e.g., facsimile, pager, email, etc.).

If desired, the customer can take appropriate action through a customerinterface. For example, the customer may send a command to the remotevalve (e.g., open until the flow rate reaches a certain level). Such acommand may be sent through the customer interface (e.g., inputting acode through a telephone tone/number sequence, inputting a command intoa web browser, or other method). The VNOC receives the command from thecustomer and records another incoming event. The VNOC then translatesthe customer incoming event into the proper network outgoing eventformat and sends the command to the remote valve for implementation.

FIG. 9 is a schematic representation of VNOC system 25 communicatingbetween various customer facing interfaces and network facinginterfaces. Customer interfaces may comprise any suitable interface overwhich a customer may communicate with the monitoring or control device.For example, customer interfaces may comprise computer interfaces suchas a web browser, an electronic mail (email) interface, or a customInternet protocol (IP) application. Customer interfaces may alsocomprise telephone interfaces such as a modem, an IVR, a facsimilemachine, and a pager. Customer interfaces may also comprise custominterfaces such as a control and monitoring host, for example, asupervisory control and data acquisition (“SCADA”) host. Other customerinterfaces are possible.

The various customer interfaces communicate with VNOC 25 over anappropriate network. For example, computer related customer interfaces(e.g., web browser, email interface, or custom 1P application)communicate with VNOC 25 over a computer network 31 such as the Internetor a local intranet. Other computer networks (WANs, LANs, etc.) arepossible. Similarly, telephone related customer interfaces (e.g., modem,IVR, fax machine, or pager) communicate with VNOC 25 over a telephonenetwork 32 and custom devices communicate with VNOC 25 over a suitablecustom network 33 (e.g., X0.25, VSAT, SCADA, wireless, etc.).

The various network facing interfaces communicate with VNOC 25 over anappropriate network. The communication may be accomplished over typicalwire line, wireless, or other network. For example, VNOC 25 communicateswith network facing interfaces using Bluetooth™, cellular, satellite,interconnected computer (i.e., the Internet), or other networks. VNOC 25communicates over networks with various third party network services.For example, VNOC 25 may communicate with third party network servicessuch as Bluetooth™ 34, MicroBurst 35, the Internet 36, Mobitex 37,OrbComm 38, GSM 39, Cellemetry 40 and other future networks 41. Thevarious third party network services may communicate with various I/Odevices. The I/O devices enable monitoring and control of varioussystems. Monitoring and control may be implemented by any suitable inputor output. For example, input and output may comprise digital, analog,AMR, or other signal formats.

Developer interfaces 42 may also communicate with VNOC 25. The developerinterfaces 42 may be used by customers or others to enable other desiredprograms and applications. For example, developer tools such asJava/Bean, ODBC/SQL, OPC, LIB/DLL, ActiveX, COM, DCOM, ORB, and others,may be used to adapt telemetry applications in communication with VNOC25.

As shown in FIG. 10, the various customer and network interfacescommunicate through the transmission of events through VNOC 25. Inboundevents may originate at the customer interface (e.g., inbound event200), or the network interface (e.g., inbound event 206). These inboundevents are processed into corresponding outbound events (e.g., outboundevents 204 and 202). As noted above, events correspond to occurrences(or the lack of an occurrence) pre-selected for customer monitoring. Inother words, the events are situations for which the customer desires tobe notified. Thus, events may comprise physical occurrences (e.g., ameter records a certain value, a pre-selected inventory item is shipped,etc.) or other less tangible occurrences (e.g., a pre-selected stockprice is reached, a certain sales volume is reached, a particular emailmessage is received, a particular time period has expired, a dat filehas been transferred, a point-to-point message is received, etc.).

For certain events a customer may desire notification. Such notificationmay comprise a report sent to the customer in a pre-selected format (orformats for multiple reports). Other events may trigger other services.For example, some events may be set up to cause an automatic responsefrom VNOC 25 (e.g., if a predetermined meter safety reading is exceeded,then automatically shut down the I/O device). Other services arepossible. Reports and services associated with an event may becollectively considered as transactions. As shown in FIG. 11,transactions may be inbound 300 or outbound 305. Such a configurationenables the reporting and processing of event data using apublish/subscribe paradigm. Reports and services triggered by an eventmay be handled as a single transaction.

FIG. 12 is a schematic representation of internal structure of VNOC 25.VNOC manager 100 manages communication between customer interfaces andnetwork interfaces. Event manager 102 enables the management of eventspassing through VNOC 25. For example, events such as incharge, onset tooffload, dependencies, concurrence, and others may be managed by eventmanager 102. Publication/subscription manager 104 enables the managementof customer subscription to, and network publication of eventsConfiguration manager 106 manages the configuration of various VNOC 25components by enabling, for example, customer specification ofinterfaces, protocols, services and other criteria. Security manager 108enables management of various security measures implemented in the VNOCsystem. For example, security measures such as access rights,revocation, auditing, and other security functions may be managed bysecurity manager 108. Error and recovery management manager 110 enablesthe management of error detection and recovery from errors. For example,error and recovery functions such as, notification, logging, recovery,backups, secondary paths, and other functions may be managed by errorand recovery manager 110. Replication redundancy manager 112 enablesvarious replication features. For example, redundancies between machinesand locations, hot failure switchovers, persistence, rollovers, andother replication features may be managed by replication redundancymanager 112. Customer billing module 114 enables, among other things,the tracking and billing of customer usage. For example, customerbilling module 114 may manage the tracking of the level of usage,accumulation of bills, charges to third party interfaces, and otherbilling functions. Audit and log module 116 enables auditing and loggingof various information. For example, location, levels, access,presentation, historical presence, and other information may be managedby audit and log module 116. Event naming module 118 manages the namingof events and may communicate with event database 120. For example,using an extensible markup language (XML) style event naming.

FIGS. 13A and 13B represent an embodiment of the VNOC architecture. Asshown in FIG. 13A, the VNOC architecture compares with the open systemsinterconnection (OSI) reference model network architecture. The OSIreference model 550 provides for various layers of network architecture(as shown in FIG. 13B). For example, the OSI layers may include aphysical layer 71, a data link layer 72, a network layer 73, a transportlayer 74, a session layer 75, a presentation layer 76 and an applicationlayer 77. In an embodiment of the VNOC, physical layer 71 may comprisethe various Ethernet, serial port, RF, modem, wireless, and other,physical connections as supported by the I/O device. Transport layer 74,network layer 73 and data link layer 72 may comprise the variousprotocols that make up the network and customer interfaces (e.g.,WinSock, TCP/IP, IPX/SPX, UDP, SLIP/PPP, and other proprietaryprotocols). The session layer 75, presentation layer 76 and applicationlayer 77 comprise the various VNOC processes described herein.

The VNOC architecture enables various features which provide forincreased flexibility. For example, the VNOC system allows uniformrepresentation of event data collected from a variety of I/O points,hand held devices, computers and networks. In addition, the reportingand receipt verification of events can be provided in any availablecustomer protocol and interface. The symmetric design also provides forthe customer to be an I/O point and provide an incoming event into VNOC25. The VNOC architecture allows one user to connect to multiple I/Opoints, hand held devices or computers (one-to-many), multiple users toconnect to one I/O point, hand held device or computer (many-to-one) andmultiple users to connect to multiple I/O points, hand held devices orcomputers (many-to-many).

Additional features of the VNOC exist. For example, users are providedwith simple and flexible interfaces, which they are accustomed to and,over which they can interact with their I/O points for feedback andcontrol purposes. Furthermore, the VNOC allows users to query the systemto retrieve desired data. Additionally, the VNOC provides the ability tosummarize data at user specified level of detail and for user specifiedperiods of time.

FIG. 14 represents a schematic of an embodiment of the VNOC system. Asshown, such an embodiment enables high availability of the VNOC byproviding multi-redundant systems (e.g., VNOC 25A, VNOC 25B, and VNOC25C). Other multi-redundant features (e.g., multi-redundant servers,connections, and geographic locations) also ensure reliability andavailability of the VNOC system.

The VNOC remote monitoring system can be combined with other relatedtechnologies to provide more sophisticated notification and/or datacollection systems. For example, two way pager notification can beemployed as an add-on to the system. Also, integrated voice response canbe employed in the system to enable the system to confirm that aparticular notification has, in fact, been received by the properpersonnel. Other features, such as fax on demand and web presence, canbe employed to provide periodic information updates via fax or internet.This feature is particularly useful when a data collection center iscollecting data from a plurality of remote monitoring systems (such asnetwork 20 shown in FIG. 2) and compiling the data for analysispurposes. A variety of other technologies can be easily interfaced withthe VNOC system to allow customization of each product to the user'sneeds. For instance, the system can be adapted for security monitoringand reporting applications to use, for example, the Mobitex PCS networkfor the transmission of video capture of intrusions or status ofmonitored area.

The systems explained in conjunction with FIGS. 1-4 and 9-14 can beemployed in a variety of different applications which are suited forremote monitoring. For example, in addition to monitoring devices suchas meters and wireless networks as discussed in FIGS. 1-4, the system ofFIGS. 14 and 9-14 may be employed to monitor devices such as vendingmachines, drop boxes, sewer and water treatment facilities, floodcontrol systems, railroad systems, waste management systems,environmental management systems, oil and gas pipelines, trafficsystems, electric, gas and water utility systems, and medical alertsystems. The system of FIGS. 14 and 9-14 may also be employed as part ofa quality management system. Other applications will be apparent topersons skilled in the art.

The wireless communication capabilities discussed in FIGS. 1-4 and 9-14of the present invention may be employed for the remote monitoring ofvending machines such as food or beverage dispensing machines. Forexample, a remote monitoring system can be installed in or near avending machine and connected to appropriate sensors to monitor suchcharacteristics as power status, product inventory, available monetarychange status and a variety of general dispensing functions to ensurethat the vending machine is operating properly at all times. Sensors maybe any conventional system for acquiring the type of data which is to bemonitored. For example, many vending machines include electroniccircuitry which acquires some or all of the data required by the remotemonitoring system of the present invention. In such a case, it is onlynecessary to connect the electronic circuitry of the vending machinewith the input/output and/or expansion ports of an appropriate interfaceand to include a wireless communication system such as a Bluetooth™wireless system.

A main power module can be connected to the available power source forthe vending machine for operation. When a remote monitoring systemdetects a problem with the vending machine, data indicating the type ofproblem, such as a malfunction or depletion of inventory, can becommunicated to the appropriate source for action. This allows servicepersonnel to be dispatched promptly when they are required. Moreover,with appropriate equipment, information about the cause of the problemcan be communicated to service personnel to provide them with an idea ofthe situation that needs to be addressed. Thus, the vending machine canbe promptly serviced, when required, and unnecessary visits to thevending machine can be eliminated.

The present invention may also be employed as part of a waste managementsystem to monitor such things as the need for pick-up at a particulardumpster, the truck count at a dumpster and/or to determine whether aparticular truck is full and needs to unload. This could be done byinterfacing conventional sensors at dumpster sites with a wirelesscommunication system such as the Bluetooth™ system. In this manner,trucks can be more efficiently deployed to make pick-ups where neededand to avoid unnecessary pick-ups. This may permit a reduction in thenumber of trucks required to service a particular area and/or allowalterations of the size or placement of dumpsters to efficientlyaccommodate the need for same.

The present invention is also applicable to monitor various aspects ofutilities including gas, electric and water utilities. For example, themeters in individual households can be replaced by, or upgraded withmeters that are enabled for wireless communication such as the metersdiscussed in conjunction with FIG. 1. These meters provide remotereporting of utility usage to a data collection center. Further, water,gas and electricity distribution systems can be monitored using thepresent invention for both failure detection and to collect data usefulto determine efficient ways to operate such distribution systems.Additionally, a variety of different key pieces of equipment employed byutilities can be monitored using the system of the present invention.

Other embodiments and uses of the invention will be apparent to thoseskilled in the art from consideration of the specification and practiceof the invention disclosed herein.

What is claimed is:
 1. A wireless network, comprising: a group ofwireless network nodes, wherein each node of the group of wirelessnetwork nodes determines one or more respective nodes of the group ofwireless network nodes to connect with, and wherein the group ofwireless network nodes is configured to form an organized network; andone or more gateways communicatively coupled to the group of wirelessnetwork nodes to provide a respective communication access point betweenthe one or more respective nodes of the group of wireless network nodesand an external network, wherein access by the one or more respectivenodes to the external network is facilitated by one or more routes fromthe one or more respective nodes to the one or more gateways defined bythe organized network.
 2. The wireless network of claim 1, wherein eachnode of the group of wireless network nodes is configured to execute aself-configuration cycle to establish the organized network.
 3. Thewireless network of claim 2, wherein the self-configuration cyclecomprises a determination of whether a number of hops to one of the oneor more gateways exceeds a maximum number of hops.
 4. The wirelessnetwork of claim 2, wherein the self-configuration cycle comprises anexamination of a measure of redundancy in connections.
 5. The wirelessnetwork of claim 2, wherein the self-configuration cycle comprises adetermination of whether a connection is made only to a group of networknodes that is searching for another network node.
 6. The wirelessnetwork of claim 2, wherein the self-configuration cycle comprises adetermination of signal strength.
 7. The wireless network of claim 2,wherein the self-configuration cycle is based on a request message thatis sent after pseudo random delays.
 8. The wireless network of claim 1,wherein each node of the group of wireless network nodes is configuredto store a routing table that comprises routing information about atleast one other wireless network node.
 9. The wireless network of claim1, each node of the group of wireless network nodes is configured toexecute a polling procedure to poll another wireless network node. 10.The wireless network of claim 1, wherein the one or more gateways storesgeographic location of wireless network nodes within a pre-specifieddistance of the one or more gateways.
 11. A wireless network method,comprising: organizing a group of wireless network nodes into anorganized network in view of a self-configuration process implemented bythe group of wireless network nodes, wherein each node of the group ofwireless network nodes determines one or more respective nodes of thegroup of wireless network nodes to connect with; and coupling the groupof wireless network nodes to one or more gateways, the one or moregateways is configured to provide a communication access point betweenthe group of wireless network nodes and an external network, whereinaccess by an additional wireless network node to the external network isfacilitated by a route that comprises a path from a first node of thegroup of wireless network nodes to the one or more gateways defined bythe organized network.
 12. The wireless network method of claim 11,wherein the organizing comprises executing, by each node of the group ofwireless network nodes, a self-configuration cycle to establish theorganized network.